home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: mxsld2.pd.infn.it!LORETI
- From: loreti@mxsld2.pd.infn.it (Maurizio Loreti)
- Subject: Re: What will happen close to 640K limit ?
- X-Nntp-Posting-Host: mxsld2.pd.infn.it
- Message-ID: <DM6HsA.652@news.cern.ch>
- Sender: news@news.cern.ch (USENET News System)
- Reply-To: loreti@mxsld2.pd.infn.it
- Organization: I.N.F.N. Padova - CDF/CMS VAXcluster
- References: <Pine.SOL.3.91.960128110843.26154C-100000@hamlet.uncg.edu>
- Date: Sat, 3 Feb 1996 02:33:45 GMT
-
- In article <Pine.SOL.3.91.960128110843.26154C-100000@hamlet.uncg.edu>, "QIAN . ZHONG" <q_zhong@hamlet.uncg.edu> writes:
- >
- >Hi, folks:
- >
- >I wrote a DOS program, with size about 512K, which is the size when I use
- >dir to check it.
- >
- >I also use dos command mem to check dos avaible memory, which gave me max
- >execute file size 560k, because there are some device driver I load in
- >the config.sys, I knew 512k is not real program size, there are some
- >stack variable and memory allocated on heap.
- >
- >Now my program is not stable, it can work for fine for couple days, then
- >it lock up. It may just lock up keyboard or screen, it may also reboot
- >PC, I wonder if because it close to 640 K limit ? How can I check the real
- >program size include stack size and heap ?
- >
- >Is PhLarp an easy package to go beyond 640 K ?
- >
- >Thanks in advance, please send me mail.
- >
- > Qian Zhong
- > Department of Chemistry.
- > UNC, Greensboro
- > Email: q_zhong@hamlet.uncg.edu
- >
- >
-
- But what is your C-language question?
- I assume you are thinking that if the program were written in FORTRAN
- its behaviour would have been different :-)
- --
- Maurizio Loreti http://mvxpd5.pd.infn.it/wwwcdf/mlo.html
- Un. of Padova, Dept. of Physics - Padova, Italy loreti@padova.infn.it
-